home *** CD-ROM | disk | FTP | other *** search
- Path: news.cc.sunysb.edu!usenet
- From: gene@calph.physics.sunysb.edu (Eugene Tyurin)
- Newsgroups: comp.lang.c,comp.programming
- Subject: Re: Assertive or Defensive?
- Date: 29 Mar 1996 18:46:25 -0500
- Organization: Institute for Theoretical Physics, Stony Brook University
- Sender: gene@calph.physics.sunysb.edu
- Message-ID: <htlokjqx7y.fsf@calph.physics.sunysb.edu>
- References: <4ioggn$3sf@dazzle.east-tenn-st.edu>
- <4itcs2$po3@B1FF.mindspring.com> <31546257.11E1@olympic.net>
- NNTP-Posting-Host: calph.physics.sunysb.edu
- In-reply-to: "Erik W. Anderson"'s message of Sat, 23 Mar 1996 12:43:03 -0800
- X-Newsreader: Gnus v5.0.15
-
- >>>>> "Erik" == Erik W Anderson <eanders@olympic.net> writes:
-
- Erik> To follow up on that point, an execellant book to check out
- Erik> is "Writing Solid Code" by Steve MacGuire published by MS
- Erik> Press under ISBN 1-55615-551-4.
-
- If this is the same as "Microsoft's Guide to Bug-Free Code" that I
- looked at some time ago, I have a *solid* problem with it.
-
- Basically, they say: we have 2 versions of code -- development and
- production (they call it "slick"). Production version has minimum of
- diagnostics, because who cares if a program crashes once in a while
- instead of exiting with proper message -- user can always reboot.
-
- Last time I used assert was to detect numerical overflow. I found the
- problem and corrected it. After that assert became redundant.
- --
- Eugene Tyurin - PhD student at ITP, Stony Brook U.
- http://www.physics.sunysb.edu/~gene/
-